Copilot had no explicit guardrail preventing it from working on tasks outside the project's defined milestones. This adds a hard scope boundary to both instruction files.

Changes

• .github/copilot-instructions.md

  • New Scope of Work section (placed immediately after Project Overview) mandating the agent only act on tasks mapped to an active milestone in MILESTONES.md
  • Milestone gate added as the first item in the Code Review Checklist — blocks proceeding if the task has no milestone backing

• COPILOT_INSTRUCTIONS.md

  • Same Scope of Work section added after the Goal section for consistency — both instruction surfaces now carry the same constraint

Rule summary

Do not implement features, fix bugs, refactor code, add tests, or make any other changes that are not part of a milestone listed in MILESTONES.md. If a requested task falls outside the defined milestones, stop and ask the maintainer rather than proceeding.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.